Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cnetlink: only check bridge for vlan_filtering on creation #429

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

KanjiMonster
Copy link
Contributor

We don't need to check for vlan_filtering being enabled every time we attach a port to the bridge, only on the first attachement of a port to the bridge.

We don't handle vlan_filtering state changes, so even if it was disabled later, we wouldn't be able to do anything about it. So let's only check the state once when populating cnetlink::bridge.

Fixes: f93b9b5 ("cnetlink: just ignore bridges with unsupported configuration")

We don't need to check for vlan_filtering being enabled every time we
attach a port to the bridge, only on the first attachement of a port to
the bridge.

We don't handle vlan_filtering state changes, so even if it was disabled
later, we wouldn't be able to do anything about it. So let's only check
the state once when populating cnetlink::bridge.

Fixes: f93b9b5 ("cnetlink: just ignore bridges with unsupported configuration")
Signed-off-by: Jonas Gorski <[email protected]>
Copy link
Contributor

@rubensfig rubensfig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rubensfig rubensfig merged commit faa7d7f into main Apr 30, 2024
5 checks passed
@rubensfig rubensfig deleted the jogo_check_vlan_aware_once branch April 30, 2024 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants